System, method, and computer-readable medium for implementing Intelligent Network service functionality in a network

ABSTRACT

A system, method and computer-readable medium for simulating intelligent network triggers in a network system are provided. A mobile terminal is configured with an intelligent network Simulator adapted to detect call events and originate simulated intelligent network triggers in response to the call events. Call progressions implemented according to the simulated intelligent network triggers may be managed or coordinated by at least one of a carrier-gateway server and an Enterprise-gateway server. Call progressions implemented by simulated intelligent network triggers may be specified according to Enterprise member policies or general Enterprise behaviors. Advantageously, if a carrier network does not support a trigger infrastructure that has capabilities of originating triggers and terminating triggers, or if a roaming agreement is not in place that allows transfer of triggers between carriers, the use of an intelligent network Simulator provides an alternative mechanism for providing IN service functionality without network support for intelligent network triggers.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/868,215, entitled “ALTERNATIVE METHOD FOR ENABLING INTELLIGENTNETWORK SERVICES” filed Oct. 5, 2007, now U.S. Pat. No. 8,024,455 andclaims priority of U.S. Provisional Ser. No. 60/854,480, entitled“ALTERNATIVE METHOD FOR ENABLING INTELLIGENT NETWORK SERVICES” filedOct. 26, 2006 incorporated herein by reference.

FIELD OF THE INVENTION

The present disclosure relates to telecommunications and, moreparticularly, to telecommunication systems including alternativemechanisms for implementing intelligent network trigger functionality.

BACKGROUND

The Intelligent Network (IN) comprises a network architecture thatallows operators to provide value-added services in addition to thestandard telecom services, e.g., Global System for Mobile Communications(GSM) services. IN infrastructure comprises an overlay of a coretelecommunications network and provides enhancements to core telephonyservices.

An IN architecture includes, among other network entities, a ServiceSwitching Function (SSF) or Service Switching Point (SSP). The SSF orSSP may be deployed with a switch or central office and functions as atrigger point at which IN services may be invoked during a call. Theswitch identifies Detection Points during a call or call setup and,responsive thereto, may invoke a query to a service control point (SCP)that contains service logic which implements the desired service. Thequery issued by the SSP to the SCP is typically referred to as atrigger. Trigger criteria are defined by the operator and may, forexample, include the calling number or the dialed number.

Some carriers may only implement a subset of the triggeringinfrastructure and not all the triggers that an application requires.Moreover, when a subscriber is roaming, triggers may not be supportedbetween the networks of different carriers. Thus, in many scenarios, INservices may be unavailable to a mobile terminal.

Heretofore, no mechanisms have been provided to support triggerfunctionality for IN based applications without involving the switchinginfrastructure.

SUMMARY OF THE INVENTION

Embodiments disclosed herein provide mechanisms for simulating INtriggers in a network system. A mobile terminal may be configured withan IN Simulator that is adapted to originate simulated IN triggers, forexample in the form of USSD messages, SMS messages, or another suitabledata structure. Call progressions implemented according to the simulatedIN triggers may be managed or coordinated by at least one of acarrier-gateway server and an Enterprise-gateway server. Callprogressions implemented by the simulated IN triggers may be specifiedaccording to Enterprise member policies or general Enterprise behaviors.In an embodiment, the IN Simulator is deployed on a mobile terminal SIMor on a mobile terminal capable of supporting a software client and isregistered as a call observer function. The IN Simulator is adapted togenerate simulated IN triggers for provisioning of IN servicefunctionality in the network. The IN Simulator may generate messagesrelated to call origination and termination events that facilitateprovisioning of IN services without the network support of conventionalIN triggers. Advantageously, if a carrier network does not support atrigger infrastructure that has capabilities of originating triggers andterminating triggers—or if a roaming agreement is not in place thatallows the transfer of these triggers between carriers—the use of an INSimulator provides an alternative mechanism that provides theinformation to a IN based application for providing IN servicefunctionality without network support for IN triggers.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingdetailed description when read with the accompanying figures, in which:

FIG. 1 is a diagrammatic representation of a network system in whichembodiments disclosed herein may be implemented for advantage;

FIG. 2 is a simplified block diagram of an exemplary mobile terminal inwhich embodiments may be implemented;

FIG. 3 is a diagrammatic representation of an exemplary softwareconfiguration of a mobile terminal adapted for originating simulatedintelligent network triggers in accordance with an embodiment;

FIG. 4 is a diagrammatic representation of a signaling flow of a mobileoriginated call to an Enterprise member implemented in accordance withan embodiment;

FIG. 5 is a diagrammatic representation of a signaling flow of anEnterprise member placing a call to another Enterprise member from anenterprise landline telephony device implemented in accordance with anembodiment;

FIG. 6 is a diagrammatic representation of a signaling flow of a calloriginated from a PSTN device to an Enterprise member in accordance withan embodiment;

FIG. 7 is a diagrammatic representation of a signaling flow of a calloriginated from a PSTN device to an Enterprise member in accordance withan embodiment;

FIG. 8 is a diagrammatic representation of a signaling flow of a calloriginated from a PSTN device to an Enterprise member in accordance withan embodiment; and

FIG. 9 is a diagrammatic representation of a signaling flow of a calloriginated from an Enterprise member's mobile terminal to anotherEnterprise member implemented in accordance with an embodiment.

DETAILED DESCRIPTION

It is to be understood that the following disclosure provides manydifferent embodiments, or examples, for implementing different featuresof various embodiments. Specific examples of components and arrangementsare described below to simplify the present disclosure. These are, ofcourse, merely examples and are not intended to be limiting. Inaddition, the present disclosure may repeat reference numerals and/orletters in the various examples. This repetition is for the purpose ofsimplicity and clarity and does not in itself dictate a relationshipbetween the various embodiments and/or configurations discussed.

FIG. 1 is a diagrammatic representation of a network system 100 adaptedto interconnect various networks and terminals deployed therein in whichembodiments disclosed herein may be implemented for advantage. Carriernetwork 110 may comprise a code division multiple access (CDMA) carriernetwork, e.g., a CDMA2000-compliant network. Carrier network 110 mayinclude any number of base transceiver stations (BTSs) 112 a-112 ccommunicatively coupled with a base station controller (BSC) 114. Eachindividual BTS 112 a-112 c under the control of a given BSC may define aradio cell operating on a set of radio channels thereby providingservice to a Mobile Terminal (MT) 125. BSC 114 manages the allocation ofradio channels, receives measurements from mobile terminals, controlshandovers, as well as various other functions as is understood. BSC 114is interconnected with a mobile services switching center (MSC) 116 thatprovides mobile terminal exchange services. BSC 114 may be additionallycoupled with a packet data serving node (PDSN) 118 that provides aconnection point between the CDMA radio access network and a packetnetwork, such as Internet 140, and provides mobility managementfunctions and packet routing services. MSC 116 may communicativelyinterface with a circuit switched network, such as the public switchedtelephone network (PSTN) 130, and may additionally be communicativelycoupled with an interworking function (IWF) 122 that provides aninterface between MSC 116 and Internet 140.

GSM carrier network 150 includes gateway Mobile Switching Center (GMSC)151 that provides an interface between PSTN 130 and carrier network 150.GMSC 151 determines which MSC currently services a called mobileterminal. Carrier network 150 includes a Switching System (SS) 152 and aBase Station System (BSS) 156. Each of SS 152 and BSS 156 contain anumber of functional units well understood by those skilled in the art,and a detailed explanation of the various components is unnecessary.Nevertheless, a cursory review of various components is provided. SS 152contains an MSC 153, a Home Location Register (HLR) 154, and a VisitorLocation Register (VLR) 155. MSCs carry out switching functions andmanage the communications between mobile phones and the PSTN 130. HLR154 comprises the central database that contains details of each mobilephone subscriber that is authorized to use the cellular core network.VLR 155 comprises a database which stores information about all themobiles terminals that are currently serviced by the associated MSC. VLR155 stores various information regarding the mobile terminals, such asthe current location area identity that specifies a particular BSC thatthe mobile station is currently serviced by.

Various other sub-systems or functional modules may, and typically are,included in SS 152, such as an Authentication Center, an EquipmentIdentity Register, or various other functions. A serving general packetradio service (GPRS) support node (SGSN) 159 may be included in GSMcarrier network 150 to facilitate provisioning of packet services to andfrom mobile terminals in network 150. GPRS provides mobility management,session management and transport for Internet Protocol packet servicesin GSM cellular packet networks.

As is understood, various GPRS infrastructure may be included in network150 to provide packet services to mobile terminals, and only SGSN 159 ofthe GPRS core network is depicted to simplify the discussion ofembodiments disclosed herein. In general, a gateway GPRS support nodemay interface the GPRS backbone with an external packet network, such asthe Internet.

SGSN 159 may interface with various subsystem of network 150. Forexample, SGSN 159 may have a Gs interface with MSC 153 and VLR 155 thatfacilitates paging and station availability notification when performingdata transfers. SGSN 159 may additionally have a Gr interface with HLR154 through which messaging may be performed, for example, over theMobile Application Part protocol. SGSN 159 may additionally have a Gbinterface with packet control unit (PCU) (not shown) of BSS 156 thatfacilitates connection of BSS 156 with SGSN 159.

Network 150 may also include a signaling system, such as a SS7 network160. SS7 network 160 provides a set of telephony signaling protocolswhich are used to set up the vast majority of the world's PSTN telephonecalls. SS7 network 160 is also used in cellular networks, such as GSMand UMTS, for circuit switched voice and packet-switched dataapplications. As is understood, SS7 network 160 includes varioussignaling nodes, such as any number of service control points (SCPs)162, signal transfer points (STPs) 164, and service switching points(SSPs) 166.

BSS 156 contains a BSC 157 that may be in communication with and incontrol of a plurality of BTSs 158 a-158 c. Each individual BTS 158a-158 c under the control of a given BSC 157 may define a radio celloperating on a set of radio channels thereby providing service to an MT,e.g., MT 126.

Network 150 may also include a short message service center (SMSC) 161adapted to deliver short message service (SMS) messages to mobileterminals. When an SMS message is sent to a user, the SMS message isstored in SMSC 161 which delivers it to the destination mobile terminalwhen the destination mobile terminal is available. As is known, the SMSmessage may be delivered via a control channel, e.g., a cell broadcastcontrol channel, or bearer channel. Network 150 may further include aUnstructured Supplementary Service Data (USSD) gateway 163 that providesreal-time or instant messaging type phone services. USSD gateway 163provides for transmission of information of GSM signaling channels. Inaccordance with embodiments disclosed herein, USSD services may be usedin conjunction with an IN simulator deployed on a mobile terminal toprovide for IN trigger service functionality as described more fullyhereinbelow, although other messaging services, such as SMS, may besimilarly utilized for implementing embodiments of the disclosure.

System 100 may include an enterprise network 170 that includes a PBX 171that provides service to any number of extensions, e.g., enterpriseterminal devices 172 a-172 n. Additionally, PSTN 130 may interface withenterprise network 170, e.g., by a tandem or other switch coupled withenterprise router 174. Enterprise network 170 may include an enterprisegateway server (GS-E) 176 that may be communicatively coupled with acarrier gateway server (GS-C) 192 deployed in, or interconnected with,carrier network 150.

The connection between GS-E 176 and GS-C 192 may be made over, forexample, session initiation protocol (SIP) or other protocols. Thisconfiguration may enable carrier network 150 to have a central point ofcontrol for interacting with multiple enterprises, and may not requirethe use of SS7 messaging to the enterprise. Rather, it is possible tohave a secure IP connection supporting SIP. This is also useful foroffering a Centrex solution for interconnecting with a carrier-hostedPBX, or for interconnecting a carrier-hosted gateway server withenterprise-hosted PBX systems. GS-C 192 may support an SS7 point codemultiplexer in which only one or two point codes are needed to addressall enterprises since GS-C 192 can identify for which enterprise amessage is intended. GS-E 176 may be adapted to provision GS-C 192automatically over an IP interface to manage subscribers, e.g., to addnew pilot directory numbers for new subscribers. In the illustrativeexample, respective users (illustratively designated “User 1” and “User2”) are allocated a respective Enterprise terminal device 172 n and 172a as well as a mobile terminal 125 and 126.

From an IT organization perspective, GS-E 176 appears as an extension toPBX 171. To carrier network 150, GS-E 176 appears as a standardin-network endpoint for delivering calls. To PBX 171, GS-E 176 appearsas a set of standard PBX endpoints (e.g., deskphones, or IP clients).GS-E 176 mediates between the two disparate sets of network protocolsand state machines.

GS-C 192 may include the network functions for both voice (gateway MSC)and data (gateway GPRS Support Node or Home Agent), VoIP capability forinterconnecting carrier network 150 with Enterprise network 170 therebyeliminating PSTN interconnect charges, a billing gateway, and anext-generation Network Services gateway that enables third party valueadded services for the enterprise, such as mobile phoneactivation/de-activation, corporate directory integration based on IMS(IP Multimedia Subsystem), or other services. GS-C 192 may also includethe element management subsystem (EMS) and a service managementsubsystem for the operational support system (OSS).

In the example depicted in FIG. 1, mobile terminals associated withEnterprise network 170 may be configured with an IN Simulator that isadapted to originate simulated IN triggers, e.g., in the form of USSDmessages, SMS messages, SIP over GPRS or CDMA evolution-data optimized(EV-DO) or another suitable data structure. Call progressionsimplemented according to the simulated IN triggers may further bemanaged or coordinated by GS-C 192 and GS-E 176, e.g., according toEnterprise member policies maintained by member database 178.

PBX 171 may include or interface with an Enterprise member database 178that stores records or profiles that define services for members ofEnterprise network 170. GS-E 176 may interface with member database 178via a provisioning interface specific to PBX 171. Enterprise memberdatabase 178 may include records that specify enterprise members and DIDnumbers of telephony devices allocated thereto. Additionally, enterprisemember database 178 may specify usage policies for Enterprise membersthat may define, for example, allowable mobile terminal usage such asroaming capabilities, various preferred call progressions to be providedto Enterprise members under various circumstances, and the like. In anembodiment, Enterprise member database 178 may specify particular policydefinitions in response to receipt of simulated IN triggers thatoriginate from a member's mobile terminal as described more fullyhereinbelow.

In accordance with an embodiment, GS-C 192 may be managed by anIntermediary carrier 190, such as a mobile virtual network operator(MVNO). In this implementation, GS-C 192 is deployed or interconnectedwith carrier network 150 but is serviced by Intermediary carrier 190.Accordingly, an MVNO may provide mobile services to global EnterpriseCustomers, e.g., by reselling carrier services, e.g., CDMA or GSMservices, combined with Intermediary Carrier Enterprise offerings.Intermediary carrier 190 provides the ability to control HLR profiles ofuser to route simulated IN-triggers that are originated and processedaccording to embodiments disclosed herein as described more fullyhereinbelow. Moreover, Intermediary carrier 190 may provide Intermediarycarrier hosting services to CDMA carriers, such as hosting GS-C andoffer Enterprise services for a monthly charge, provide internationalsupport for GS-C services as an option to an Enterprise, and the like.

FIG. 2 is a simplified block diagram of an exemplary mobile terminal 125in which embodiments may be implemented. Mobile terminal 125 includes anantenna 202 that may be coupled with an RF switch 204, e.g., a duplexer,coupled with an RF transceiver 206. Transceiver 206 may be coupled withan analog baseband 208 that may handle a variety of analog signalprocessing functions. In the present example, analog baseband 208 isinterconnected with a microphone 210, a keypad 212, a vibrator 214 orother ring alert mechanism, a headset speaker 216, and a loudspeaker 230for output of speakerphone and incoming call alert audio. Analogbaseband 208 may include or interface with an analog to digitalconverter for converting analog input supplied to microphone 210 into adigital format that may be supplied to a digital baseband 218. Digitalbaseband 218 may interface with various digital components of mobileterminal 125, such as a memory 220, a subscriber identity module (SIM)222, and a liquid crystal display controller 226 that drives a display228. Memory 220 may be implemented as a flash memory, a random accessmemory, an electronically erasable programmable read-only memory,another solid state device, or a combination thereof. Digital baseband218 may additionally include or interface with one or more encoders,digital to analog converters, or other modules. An operating system(I/S) 234A may interface with Analog Baseband 208, and Digital Baseband218 for enabling the execution of client software application 234B. Apower supply 232 may be coupled with various system modules as isunderstood. In accordance with an embodiment, an IN simulator isdeployed on SIM 222 or client software application 234B that is adaptedto generate simulated IN triggers for provisioning of IN servicefunctionality in a network system such as system 100 depicted in FIG. 1.

The implementation of mobile terminal 125 depicted in FIG. 2 isexemplary only, and mobile terminal 125 may be implemented as anysuitable device adapted to interface with a carrier network. Mobileterminal 125, also referred to as a user equipment (UE), may beimplemented as a personal digital assistant (PDA), a mobile phone, acomputer, or another device adapted to interface with a carrier network.

FIG. 3 is a diagrammatic representation of an exemplary softwareconfiguration 300 of a mobile terminal, e.g., mobile terminal 125,adapted for originating simulated IN triggers in accordance with anembodiment. In the exemplary configuration of FIG. 3, the mobileterminal is configured with access network-specific software entities360, e.g., protocol and driver software associated with a particularaccess network technology, such as GSM, UMTS, CDMA or another suitableradio access network, and is dependent on the particular cellularnetwork in which the mobile terminal is to be deployed. Whileconfiguration 300 depicts a mobile terminal adapted for deployment in asingle access network technology type, the mobile terminal may beimplemented as a multi-mode device and may accordingly include aplurality of access-specific entities in accordance with an embodiment.The particular configuration 300 is illustrative only and is providedonly to facilitate an understanding of embodiments disclosed herein.

In the illustrative example, configuration 300 includes a cellular modemdriver 302 for providing a physical interface with the access network inwhich the mobile terminal is deployed. An access-stratum 304 and anon-access stratum 306 may be included in configuration 300. A cellularradio interface 308 may be communicatively coupled with lower layers ofconfiguration 300 and may additionally interface with network andsession management layers, e.g., a network stack 310 such as a TCP/IPlayer.

Configuration 300 includes an IN simulator 312 for providing IN servicefunctionality in accordance with an embodiment. Additionally,configuration 300 includes an operating system 314, such as Symbian,Blackberry O/S, or another operating system suitable for mobileapplications, and may coordinate and provide control of variouscomponents within the mobile terminal.

In an embodiment, IN Simulator 312 is registered as a call observerfunction in mobile terminal 125. Accordingly, mobile terminal 125notifies IN Simulator 312 of call origination and termination events,and IN Simulator 312 may generate messages related to call originationand termination events that facilitate provisioning of IN serviceswithout the network support of IN triggers. Messages generated by INSimulator 312 that facilitate provisioning of IN services are referredto herein as simulated IN triggers.

If a carrier network, e.g., GSM carrier network 150, doesn't support atrigger infrastructure that has capabilities of originating triggers andterminating triggers—or if a roaming agreement is not in place thatallows the transfer of these triggers between carriers—the use of INSimulator 312 provides an alternative mechanism that provides the sameinformation to an IN based application in accordance with an embodiment.IN Simulator 312 is thereby adapted to mimic the IN triggeringinfrastructure and provides mechanisms for implementing IN triggerservice functionality without network support for IN triggers.

Various simulated trigger mechanism that are facilitated by IN Simulator312 are described below. The described trigger mechanisms areillustrative only and are provided to facilitate an understanding of thedisclosed embodiments, and implementation of embodiments disclosedherein is not restricted to the described triggers.

To create an IN-simulated origination trigger for Detection Point 2(DP2) “Collected Information” structure, the following steps may beperformed. IN Simulator 312 is registered as a call observer functionand receives the call origination event from the originating mobileterminal. IN Simulator 312 converts the origination request into a datamessage using a method such as USSD, SMS, GPRS or other mechanism thatis sent to the IN-based application with the origination messageparameters as appropriate. In the exemplary network architecture, theIN-based application may be run by GS-C 192 in conjunction with GS-E176. That is, the IN service progression is managed by at least one ofGS-C 192 and GS-E 176. The IN-based application run by GS-C 192 and/orGS-E 176 performs its application processing and returns the response tothe simulated Origination Trigger via the data network such as USSD,SMS, etc. These responses may include Connect, Continue and Release. Ifthe data message contains a Connect response, IN Simulator 312 will setup an originating call with the digits provided in the data messageinstead of the original dialed digits. If the data message contains aContinue response, IN Simulator 312 will set up an originating call tothe original dialed string. If the data message contains a Releaseresponse, IN Simulator 312 can provide treatment such as providing atone to the user or display a message indicating that the call could notbe completed.

To create an IN-simulated origination trigger DP for an origin-Busy(“O-Busy”) structure the following general procedure may be performed.IN Simulator 312 is registered as a call observer function and receivesthe busy end point notification from the switching infrastructure. INSimulator 312 converts the origination request into a data message,e.g., using USSD, SMS, etc., that is sent to the IN based application,e.g., run by GS-C 192, with the origination message parameters asappropriate. The IN based application performs its applicationprocessing and returns the response to the Origination Trigger via adata message.

To create an IN-simulated origination trigger DP for an origin-No Answer(“O-No Answer”) structure, the following general procedure may beperformed. IN Simulator 312 is registered as a call observer functionand receives a disconnect notification from the network prior to thecall being answered. IN Simulator 312 converts the origination requestinto a data message to the IN based application with the originationmessage parameters as appropriate. The IN based application performs itsapplication processing and returns the response to the OriginationTrigger via a data message.

To create an IN-simulated origination trigger DP for an origin-Answer(“O-Answer”) structure the following general procedure may be performed.IN Simulator 312 is registered as a call observer function and receivesthe answer indication from the switching network. IN Simulator 312converts the origination request into a data message that is transmittedto the IN based application with the origination message parameters asappropriate. The IN based application performs its applicationprocessing and returns the response to the Origination Trigger via adata message.

To create an origination trigger DP for an origin-Disconnect(“O-Disconnect”) structure, the following general procedure may beperformed. IN Simulator 312 is registered as a call observer functionand receives the disconnect indication from the network or the end keyinput from the user. IN Simulator 312 converts the origination requestinto a data message that is transmitted to the IN based application runby the GS-C with the origination message parameters as appropriate. TheIN based application performs its application processing and returns theresponse to the IN-simulated Origination Trigger via a data message.

To create an IN-simulated termination trigger DP12 for “TerminatingAttempt Authorized” the following general procedure may be performed. INsimulator 312 receives the call termination event from the mobileterminal. IN simulator 312 converts the call termination into a datamessage and transmits the data message to the IN based application withthe termination message parameters as appropriate. The IN basedapplication performs its application processing and returns the responseto the IN-simulated Termination trigger via a data message. Theseresponses may include Connect, Continue or Release. If the data messagecontains a Connect response, IN simulator 312 uses the Call DeflectionSupplementary Service to redirect the call to the endpoint provided inthe connect response. If the data message contains a Continue response,IN Simulator 312 allows the call to be delivered and proceeds to ringthe mobile terminal. If the data message contains a Release response, INSimulator 312 does not accept the call and terminates to switchinginfrastructure.

An IN-simulated Termination Trigger DP13 for “Busy” can be created by INSimulator 312 in the case when the IN based application infrastructurealso provides an alternative to call waiting services. This is because abusy determination is typically handled by the switching infrastructurewithout any knowledge by the handset. However, this can be replicated byimplementing an alternative call waiting service in accordance with anembodiment. The following procedure may generally be performed to createan IN-simulated DP13 “Busy” trigger. IN Simulator 312 receivesnotification of a terminating call. A data message is sent to the INapplication, and the IN application sends back a connect message toindicate to connect the call to the IN application. The data messagereceived by IN simulator 312 contains the connect-to information. INsimulator 312 uses the Call Deflection Supplementary Service to redirectthe call to the end point received in the connect response. The INapplication, receiving the call termination, routes the call to theterminating mobile via the switching infrastructure. IN Simulator 312will again receive notification of this terminating call from the INapplication. The call should be presented to the user with the originalcalling line ID information provided. IN simulator 312 receives anothernotification during the current call. This call is not answered so thatend point is receiving ringing. A data message is sent to the INapplication. The IN application sends back a connect message to indicateto connect the call to the IN application. The data message received byIN simulator 312 contains the connect to information. IN simulator 312uses the Call Deflection Supplementary Service to redirect the call tothe end point received in the connect response. IN simulator 312provides a call waiting indication to the user via a tone and thedisplay of who is calling. If the user decides to accept the incomingcall by pressing “send”, IN simulator 312 issues a data message to theIN application. When the IN application receives the message that theuser wants to accept the new incoming call, it answers the new call andconnects to the current leg that it has up to the mobile and places thecurrent leg on hold. IN Simulator 312 receives notification of theterminating call while currently handling the two established calls. Adata message is sent to the IN application, and the IN application sendsback a connect message to indicate to connect the call to the INapplication. The data message received by IN simulator 312 contains theconnect to information. IN simulator 312 uses the Call DeflectionSupplementary Service to redirect the call to the IN application. The INapplication, receiving the call termination and knowing that the user iscurrently handling two calls—gives busy treatment to the new call andcan create a DP-13 to itself or other application requiring the DP-13Busy trigger.

In accordance with an embodiment, an IN-simulated Terminating Triggerfor DP14 “No Answer” may be generated and processed according to twogeneral procedures. A No Answer DP can occur in two ways—when the mobileis not registered on the network, and when the mobile rings but the userchooses not to answer. These two general scenarios are processedaccording to disclosed embodiments as follows. When the mobile terminalis not registered on the network, the call forwarding number of themobile is set to the IN application When a call is received at the INapplication, the IN application creates a no answer trigger for thisreceived call.

When the mobile terminal is registered but the user doesn't answer thecall, IN Simulator 312 is informed that a terminating call has beendelivered to the phone and detects that the user has selected the endbutton when the call is “ringing”. In this instance, IN Simulator 312generates and sends a data message to the IN application providing theIN-simulated No Answer Trigger. The IN application may then provideeither a release or connect response to the termination trigger. If INsimulator 312 receives a connect response, IN simulator 312 uses theCall Deflection Supplementary Service to redirect the call to the INapplication. If IN simulator 312 receives a release response, the callcan be released from the switching infrastructure.

To create an IN-simulated termination trigger for DP15 “Answer”, thefollowing general procedure may be performed. IN simulator 312 receivesthe send or answer indication from the mobile terminal. IN simulator 312converts the event into a data message to the IN-based application withthe termination message parameters as appropriate. The IN basedapplication performs it application processing and returns the responseto the Termination trigger via a data message.

To create an IN-simulated termination trigger for DP17 “Disconnect” thefollowing general procedure may be performed. IN simulator 312 receivesthe end key or disconnect indication from the mobile terminal. INsimulator 312 converts the event in to a data message and sends the datamessage to the IN based application with the termination messageparameters as appropriate. The IN based application performs itsapplication processing and returns the response to the IN-simulatedTermination trigger via a data message.

To create an IN-simulated termination trigger for DP18 “Abandon” thefollowing general procedure may be performed. IN simulator 312 receivesthe disconnect indication from the network prior to call answeringstate. IN simulator 312 converts the event in to a data message that istransmitted to the IN-based application with the termination messageparameters as appropriate. The IN based application performs itsapplication processing and returns the response to the IN-simulatedTermination trigger via a data message.

FIG. 4 is a diagrammatic representation of a signaling flow 400 of amobile originated call to an Enterprise member implemented in accordancewith an embodiment. In the present example, assume the originatingmobile terminal 125 is equipped with an instance of IN Simulator 312described with reference to FIG. 3, and that the user of mobile terminal125 uses abbreviated dialing for calling User 2's Enterprise telephonedevice 172 a. That is, User 1 placing the call dials User 2's Enterpriseextension rather than the full directory number assigned to device 172a. Upon entry of the dialed number and a call setup command, e.g., byselecting Send at mobile terminal 125, IN simulator 312 identifies thecall origination event. IN simulator 312 then collects the callinformation suitable for generating an IN-simulated origination trigger(DP 2), and creates an IN-simulated DP 2 trigger from the collected callinformation. In the illustrative example, the collected informationcorresponding to a DP 2 trigger is formulated in a USSD message. TheUSSD message is then transmitted through the radio access network, e.g.,via BTS 158 a and BSC 157, wherein the USSD message is received at MSC153 (step 402). MSC 153 accordingly routes the USSD message to USSDgateway 163 (step 404) that in turn forwards the USSD message to GS-C192 (step 406). Thus, in this manner, the collected informationformulated in the USSD message is transmitted to GS-C 192 in a mannerthat replaces a trigger event detected at an SSP. Accordingly, carriernetwork 150 is not required to support the IN infrastructure or,alternatively, mobile terminal 125 is not required to have any INservice agreement with carrier network 150 for invoking an IN servicefunction.

On receipt of the USSD message, GS-C 192 may recognize the called orcalling party as an Enterprise member and issue an INVITE message toGS-E 176 (step 408). GS-E 176 may query Enterprise member database 178to determine an appropriate call progression, e.g., whether to releasethe call, terminate the call with the dialed party's fixed enterprisetelephony device, the dialed party's mobile terminal, or other suitablecall progression. In the present example, assume GS-E 176 replies toGS-C 192 with a SIP redirection, e.g., a SIP 302 message, that includesa redirection address, e.g., a pilot directory number (PDN) assigned todevice 172 a (step 410). GS-C 192, in turn, includes the PDN in a USSDmessage that is transferred to USSD gateway 163 (step 412) which routesthe USSD to mobile terminal 125 (step 414).

The USSD including the PDN is then conveyed to IN simulator 312 whichinvokes an outbound call at mobile terminal 125 directed to the PDN(step 416). MSC, on receipt of the call setup request, determines thePDN to be a directory number external to carrier network 150 and routesthe call set up to GMSC 151 (step 418). GSMC 151 recognizes the PDN as apilot number of PBX 171 and routes the call termination attempt thereto(step 420). PBX 171 may then issue an INVITE message with the PDN as thecalled party directory number to GS-E 176 (step 422). GS-E 176 resolvesthe user directory number associated with the PDN and replies to PBX 171(step 424), e.g., with the extension assigned to User 2's land linetelephony device 172 a. The call set up is then completed with device172 a (step 426).

FIG. 5 is a diagrammatic representation of a signaling flow 500 of anEnterprise member placing a call to another enterprise member from anenterprise landline telephony device 172 a implemented in accordancewith an embodiment. Assume for illustrative purposes that the callednumber is supplied as the short code, or extension, of Enterprisetelephony device 172 n assigned to User 1, and that the call is placedat Enterprise telephony device 172 a. The call set up request istransmitted from device 172 a to PBX 171 (step 502), which in turntransmits a telephone application program interface (TAPI) function callto GS-E 176 (step 504). In accordance with an embodiment, GS-E 176 maymaintain or interface with a record allocated for called User 1 thatassociates the directory number of Enterprise telephony device 172 n,the short code of device 172 n, and the directory number of mobileterminal 125. In this instance, the call may be “forked” or generallyplaced in parallel to the called Enterprise telephony device as well asmobile terminal 125 associated with the called user. To this end, anINVITE message is transmitted from GS-E 176 to PBX 171 that specifiesthe extension of device 172 n (step 506). The INVITE may then betransmitted to device 172 n (step 508).

A second INVITE message may be generated and transmitted from GS-E 176to GS-C 192 that specifies the directory number of mobile terminal 125(step 510). Transmission and generation of the INVITE message thatspecifies mobile terminal 125 may be made substantially concurrentlywith the INVITE message transmitted toward the Enterprise landlinetelephony device 172 n. GS-C 192 may then transmit a send routinginformation (SRI) message to HLR 154 that maintains subscription recordsof mobile terminal 125 (step 512). HLR 154 then identifies the servicingMSC 153 of mobile terminal 125 and transmits a provide roaming number(PRN) message thereto (step 514). MSC 153 then transmits a PRI responsemessage to HLR 154 that includes the mobile station roaming numberassigned to mobile terminal 125 (step 516) which is forwarded to GS-C192 (step 518). GS-C 192 then transmits a SIP redirection message thatincludes the mobile station roaming number of mobile terminal 125 as atemporary local directory number (TLDN) to GS-E 176 (step 520). AnINVITE message is then transmitted to PBX 171 (step 522) that includesthe TLDN number that allows PBX 171 to complete the call setup throughGMSC 151 which uses the TLDN for routing the call to mobile terminal 125via the appropriate MSC 153 (step 524). Accordingly, both devices 125and 172 n may provide an incoming call alert, and User 1 assigneddevices 125 and 172 n may accept the call at either device.

FIG. 6 is a diagrammatic representation of a signaling flow 600 of acall originated from a PSTN device 625 to an Enterprise member inaccordance with an embodiment. Assume for illustrative purposes that thecalled number is the directory number assigned to landline device 172 nassigned to User 1. The call set up request is transmitted from device625 to PBX 171 (step 602), which in turn transmits a TAPI function callto GS-E 176 (step 604). GS-E 176 may evaluate the dialed number andidentify mobile terminal 125 as being associated with landline device172 n. That is, GS-E 176 may identify mobile terminal 125 and device 172n as both assigned to the called Enterprise member, and may determinethe directory number of mobile terminal 125. Thus, GS-E 176 mayfacilitate establishing a call origination to both landline device 172 nand mobile terminal 125. To this end, GS-E 176 transmits an INVITEmessage to PBX 171 that specifies the extension of device 172 n (step606), and PBX 171 provides an alert to device 172 n (step 608).

A second INVITE message may be generated and transmitted from GS-E 176to GS-C 192 that specifies the directory number of mobile terminal 125(step 610). Transmission and generation of the INVITE message thatspecifies mobile terminal 125 may be made substantially concurrentlywith the INVITE message transmitted toward the Enterprise network foralerting device 172 n of an incoming call. GS-C 192 may then transmit anSRI message to HLR 154 that maintains subscription records of mobileterminal 125 (step 612). HLR 154 then identifies the servicing MSC 153of mobile terminal 125 and transmits a PRN message thereto (step 614).MSC 153 then transmits a PRN response message to HLR 154 that includesthe mobile station roaming number assigned to mobile terminal 125 (step616) which is forwarded to GS-C 192 (step 618). GS-C 192 then transmitsa SIP redirection message that includes the mobile station roamingnumber of mobile terminal 125 as a temporary local directory number(TLDN) to GS-E 176 (step 620). An INVITE message is then transmitted toPBX 171 (step 622) that includes the TLDN number that allows PBX 171 tocomplete the call setup through GMSC 151 which uses the TLDN for routingthe call to mobile terminal 125 via the appropriate MSC 153 (step 624).Accordingly, both devices 172 n and 125 assigned to the calledEnterprise member, User 1, have a termination attempt placed thereto.

FIG. 7 is a diagrammatic representation of a signaling flow 700 of acall originated from a PSTN device 725 to an Enterprise member inaccordance with an embodiment. In the illustrative example, assume thedialed number is assigned to an Enterprise member's mobile terminal 125.The call set up request is transmitted from device 725 to GMSC 151 (step702), which in turn forwards the call request to MSC 153 currentlyservicing mobile terminal 125 (step 704). In the present example, assumemobile terminal 125 is configured with an IN Simulator 312. Accordingly,on receipt of the call termination attempt at mobile terminal 125, INSimulator 312 receives or is otherwise notified of the call terminationevent. In accordance with an embodiment, IN Simulator 312 may beconfigured to recognize that carrier network 150 does not support INtriggers, or that IN triggers or otherwise unavailable for mobileterminal 125, e.g., by a lack of a suitable agreement with carriernetwork 150. IN simulator 312 may then temporarily suppress or otherwiseprohibit an incoming call alert notification at mobile terminal 125. INSimulator 312 collects event information suitable for creating anIN-simulated DP 12 trigger in the form of a data message, e.g., a USSDmessage, that is to be transmitted to the IN based application hosted byGS-C 192 with the termination message parameters as appropriate. TheUSSD message is then transmitted through the radio access network toUSSD gateway 163 (step 708) that in turn forwards the USSD message toGS-C 192 (step 710). Thus, in this manner, the collected informationformulated in the USSD message is transmitted to GS-C 192 in a mannerthat replaces a conventional IN trigger. Accordingly, carrier network150 is not required to support the IN infrastructure or, alternatively,mobile terminal 125 is not required to have any IN service agreementwith carrier network 150 for invoking an IN service.

On receipt of the USSD message, GS-C 192 may recognize the called partyas an Enterprise member and issue an INVITE message to GS-E 176 (step712) and may await receipt of a response as to how to proceed with thecall. GS-E 176 may query Enterprise member database 178 to determine anappropriate call progression, e.g., whether to terminate the call withthe dialed party's fixed enterprise telephony device, the dialed party'smobile terminal, or other suitable call progression. In the illustrativeexample, assume GS-E 176 replies to GS-C 192 with a policy allowance,e.g., via a SIP 302 message with a Continue directive (step 714). Thedetermination of a policy allowance by GS-E 176 may be made, forexample, according to the called Enterprise member's profile oraccording to a general Enterprise behavior. GS-C 192, in turn,formulates a USSD message addressed to mobile terminal 125 that istransferred to USSD gateway 163 which includes a directive to continuewith the call (step 716) which routes the USSD message to mobileterminal 125 (step 718). The USSD message is conveyed to IN Simulator312 which reads the Continue directive therefrom. Accordingly, INSimulator 312 invokes processing to continue with the call terminationat which point an alert is generated, e.g., by IN Simulator 312, tonotify the user of the incoming call. The call termination may then becompleted when the call is accepted at mobile terminal 125.

FIG. 8 is a diagrammatic representation of a signaling flow 800 of acall originated from a PSTN device 825 to an Enterprise member inaccordance with an embodiment. In the illustrative example, assume thedialed number is assigned to an Enterprise member's mobile terminal 125.The call set up request is transmitted from device 825 to GMSC 151 (step802), which in turn forwards the call request to MSC 153 currentlyservicing mobile terminal 125 (step 804). In the present example, assumemobile terminal 125 is configured with an IN Simulator 312. Accordingly,on receipt of the inbound call attempt at mobile terminal 125, INSimulator 312 receives or is otherwise notified of the call terminationevent. In accordance with an embodiment, IN Simulator 312 may beconfigured to recognize that carrier network 150 does not support INtriggers, or that IN triggers or otherwise unavailable for mobileterminal 125. IN simulator 312 may then temporarily suppress orotherwise prohibit an incoming call alert notification at mobileterminal 125. IN Simulator 312 collects event information suitable forcreating an IN-simulated DP 12 trigger in the form of a data message,e.g., a USSD message, to the IN based application with the terminationmessage parameters as appropriate. The USSD message is then transmittedthrough the radio access network to USSD gateway 163 (step 808) that inturn forwards the USSD message to GS-C 192 (step 810). GS-C 192 hosts anIN based application that performs application processing and returnsthe response to the IN-simulated Termination trigger via a data message.These responses may include Connect, Continue or Release. Thus, in thismanner, the collected information formulated in the USSD message istransmitted to GS-C 192 in a manner that replaces a conventional INtrigger. Accordingly, carrier network 150 is not required to support theIN infrastructure or, alternatively, mobile terminal 125 is not requiredto have any IN service agreement with carrier network 150 for invokingan IN service.

On receipt of the USSD message, GS-C 192 may recognize the called partyas an Enterprise member and issue an INVITE message to GS-E 176 (step812) and await call processing instructions therefrom. GS-E 176 maydetermine a policy for processing the call, e.g., release, continue, orconnect the call based on, for example, the called Enterprise member'sprofile. To this end, GS-E 176 may query Enterprise member database 178to determine an appropriate call progression, e.g., whether to allow ordisallow the call, whether to terminate the call with the dialed party'sfixed Enterprise telephony device, the dialed party's mobile terminal,or other suitable call progression. In the illustrative example, assumeGS-E 176 replies to GS-C 192 with a policy allowance, e.g., via a SIP302 message (step 814). In the present example, assume the policyallowance message transmitted from GS-E 176 to GS-C 192 includes adirective to continue with the call, and that the call is to beredirected through Enterprise network 170. To this end, the replyprovided to GS-C 192 from GS-E 176 will include a PDN to which the callis to be deflected. GS-C 192, in turn, formulates a USSD messageaddressed to mobile terminal 125 that is transferred to USSD gateway 163which includes a call deflect directive (step 816) which routes the USSDmessage to mobile terminal 125 (step 818). The USSD message is conveyedto IN Simulator 312 which reads the call deflect directive and PDNtherefrom. IN Simulator 312 then initiates the call deflectionprocedure, e.g., by transmitting a Call Deflection Invoke message thatincludes the PDN as the Deflect To Number to MSC 153 (step 820). In thepresent example, the PDN number is recognized as associated with PBX171. Accordingly, the call termination attempt is routed to PBX 171(step 820), at which point a termination attempt may be made withtelephony device 172 n associated with User 1 (step 822). Likewise, atermination attempt may additionally be made to mobile terminal 125 thatis redirected from Enterprise network 170 back to mobile terminal 125(step 824).

FIG. 9 is a diagrammatic representation of a signaling flow 900 of acall originated from an Enterprise member (User 1) mobile terminal 125to another Enterprise member (User 2) implemented in accordance with anembodiment. In the illustrative example, assume mobile terminal 125 isadapted with an IN Simulator 312 and the dialed number is assigned tothe called party's Enterprise landline telephone device 172 a. Uponentry of the dialed number and a call setup command, e.g., by selectingSend at mobile terminal 125, IN simulator 312 identifies the callorigination event. IN simulator 312 then collects the call informationsuitable for generating an IN-simulated origination trigger DP 2, andcreates a simulated DP 2 trigger from the collected information. In theillustrative example, the collected information corresponding to a DP 2trigger is formulated in a USSD message. The USSD message is thentransmitted through the radio access network, e.g., via BTS 158 a andBSC 157, wherein the USSD message is received at MSC 153 (step 902). MSC153 accordingly routes the USSD message to USSD gateway 163 (step 904)that in turn forwards the USSD message to GS-C 192 (step 906). GS-C 192hosts an IN based application that performs application processing andreturns the response to the IN-simulated Termination trigger via a datamessage. These responses may include Connect, Continue or Release.

On receipt of the USSD message, GS-C 192 may recognize the party as anEnterprise member and communicate the call origination to GS-E 176 (step908). GS-E 176 may query Enterprise member database 178 to determine anappropriate call progression, e.g., to connect, continue, or release thecall, and if the call is to be connected, whether to connect the callwith the dialed party's fixed enterprise telephony device, the dialedparty's mobile terminal or other alternative. In the illustrativeexample, assume the mobile terminal is currently operating at aninternational carrier or other carrier for which mobile terminal 125faces long distance charges for terminating the call. In this instance,GS-E 176 may recognize mobile terminal 125 as having roamed into aninternational carrier or other carrier for which long distance chargesmay apply. Accordingly, GS-E 176 may reply to GS-C 192 with a call backresponse (step 910). GS-C 192 formulates a USSD message that includesthe call back directive and transmits the USSD message to USSD gateway163 (step 912) which, in turn, forwards the USSD message to mobileterminal 125 (step 914). The Call Back directive is read from the USSDmessage by IN Simulator 312. IN Simulator 312 is configured to recognizethe Call Back directive and place mobile terminal 125 in a wait state.

Prior, subsequent, or substantially concurrent with the generation andtransmission of the response from GS-E 176 to GS-C 192 at step 910, GS-E176 may transmit an INVITE message to PBX 171 that is transmitted toEnterprise device 172 a, that is the device to which the original callwas placed (step 918 a), which conveys the call termination attempt todevice 172 a (step 920 a). Substantially concurrently with transmissionof the INVITE message directed to device 172 a, a second INVITE messageaddressed to mobile terminal 125 that originated the call is transmittedfrom GS-E 176 to PBX 171 (step 918 b), which in turn conveys thetermination attempt to mobile terminal 125 (step 920 b). On receipt ofthe termination attempt at mobile terminal 125, IN Simulator 312 may beconfigured to recognize the inbound call as a call back for thepreviously placed call, and IN Simulator 312 may be configured to outputa ringback tone, rather than a ring tone associated with an inboundcall. Thus, from a user perspective, the inbound call terminationappears as an outbound call consistent with the call placement made bythe user of mobile terminal 125. Alternatively, the ringback tone may begenerated upon transmission of the USSD message at step 902 andcontinued throughout the call back procedure until the called partyanswers the call at device 172 a. Accordingly, the calling party may beconnected with the called party through the call back procedure, andinternational charges for the call may be substantially lower byreceiving a call termination fee, rather than a call origination fee,applied for the roaming terminal 125.

As described, embodiments disclosed herein provide mechanisms forsimulating IN triggers in a network system. A mobile terminal may beconfigured with an IN Simulator that is adapted to originate simulatedIN triggers, for example in the form of USSD messages, SMS messages, oranother suitable data structure. Call progressions implemented accordingto the simulated IN triggers may be managed or coordinated by at leastone of a carrier-gateway server and an Enterprise-gateway server. Callprogressions implemented by the simulated IN triggers may be specifiedaccording to Enterprise member policies or general Enterprise behaviors.The IN Simulator may be deployed on a mobile terminal SIM or on a mobileterminal capable of supporting a software client and is registered as acall observer function. The IN Simulator is adapted to generatesimulated IN triggers for provisioning of IN service functionality inthe network. The IN Simulator may generate messages related to callorigination and termination events that facilitate provisioning of INservices without the network support of conventional IN triggers.Advantageously, if a carrier network does not support a triggerinfrastructure that has capabilities of originating triggers andterminating triggers—or if a roaming agreement is not in place thatallows the transfer of these triggers between carriers—the use of an INSimulator provides an alternative mechanism that provides theinformation to a IN based application for providing IN servicefunctionality without network support for IN triggers.

Although the specific network architecture and nomenclature in which amobile terminal featuring an IN Simulator are depicted and describedaccording to the GSM, it is understood that this is done so forillustrative purposes only and that the network architecture on whichembodiments disclosed herein may be applied is not limited to anyparticular standard, but rather may be equivalently implemented on anyother communications system supporting any variety of cellularcommunication systems, e.g. D-AMPS, CDMA, IS-41, ANSI-41, UMTS, etc.

The illustrative block diagrams depict process steps or blocks that mayrepresent modules, segments, or portions of code that include one ormore executable instructions for implementing specific logical functionsor steps in the process. Although the particular examples illustratespecific process steps or procedures, many alternative implementationsare possible and may be made by simple design choice. Some process stepsmay be executed in different order from the specific description hereinbased on, for example, considerations of function, purpose, conformanceto standard, legacy structure, user interface design, and the like.

Aspects of the present invention may be implemented in software,hardware, firmware, or a combination thereof. The various elements ofthe system, either individually or in combination, may be implemented asa computer program product tangibly embodied in a machine-readablestorage device for execution by a processing unit. Various steps ofembodiments of the invention may be performed by a computer processorexecuting a program tangibly embodied on a computer-readable medium toperform functions by operating on input and generating output. Thecomputer-readable medium may be, for example, a memory, a transportablemedium such as a compact disk, a floppy disk, or a diskette, such that acomputer program embodying the aspects of the present invention can beloaded onto a computer. The computer program is not limited to anyparticular embodiment, and may, for example, be implemented in anoperating system, application program, foreground or background process,driver, network stack, or any combination thereof, executing on a singlecomputer processor or multiple computer processors. Additionally,various steps of embodiments of the invention may provide one or moredata structures generated, produced, received, or otherwise implementedon a computer-readable medium, such as a memory.

Although embodiments of the present disclosure have been described indetail, those skilled in the art should understand that they may makevarious changes, substitutions and alterations herein without departingfrom the spirit and scope of the present disclosure.

The invention claimed is:
 1. A method, comprising: receiving a callevent at an intelligent network simulator application operating on amobile terminal; collecting, by the intelligent network simulatorapplication, information related to the call event; generating, by theintelligent network simulator application, a message including theinformation collected by the intelligent network simulator application;transmitting the message to a first gateway server deployed in a carriernetwork; recognizing the message as a comprising a simulated intelligentnetwork trigger; informing a second gateway server deployed in anenterprise network of the simulated intelligent network trigger, whereinthe mobile terminal is allocated to a member of the enterprise network;processing the simulated intelligent network trigger according to policyof the enterprise network; and informing the intelligent networksimulator application to perform at least one of establish the callevent, answer the call event, disconnect the call event and abandon thecall event.
 2. The method of claim 1, wherein receiving the call eventcomprises receiving one of a call origination event and a calltermination event.
 3. The method of claim 1, wherein generating themessage comprises generating one of an unstructured supplementaryservice data message, a short message service message, a SIP messageover at least one of GPRS, EDGE, UMTS, CDMA EV-DO, WiMAX and LTE.
 4. Themethod of claim 1, comprising transmitting the message to a network nodeutilizing one of an unstructured supplementary service data gateway, ashort message service center, or a data gateway for at least one ofGPRS, EDGE, UMTS, CDMA EV-DO, WiMAX and LTE.
 5. The method of claim 1,comprising processing the call according to a policy of the enterprisenetwork.
 6. The method of claim 1, wherein the intelligent networksimulator application is stored on a subscriber identity module of themobile terminal and wherein the mobile terminal is capable of supportinga software client.
 7. The method of claim 1, further comprisingconfiguring the intelligent network simulator application as a callobserver function on the mobile terminal.
 8. A non-transitorycomputer-readable storage medium having computer-executable instructionsfor execution by a processing system, the computer-executableinstructions being executed by a processor to perform: receiving a callevent at an intelligent network simulator application operating on amobile terminal; collecting, by the intelligent network simulatorapplication, information related to the call event; generating, by theintelligent network simulator application, a message including theinformation collected by the intelligent network simulator application;transmitting the message to a first gateway server deployed in a carriernetwork; recognizing the message as comprising a simulated intelligentnetwork trigger; informing a second gateway server deployed in anenterprise network of the simulated intelligent network trigger, whereinthe mobile terminal is allocated to a number of the enterprise network;processing the simulated intelligent network trigger according to apolicy of the enterprise network; receiving a call event at anintelligent network simulator application operation on the mobileterminal; and informing the intelligent network simulator application toperform at least one of establish the call event, answer the call event,disconnect the call event and abandon the call event.
 9. Thenon-transitory computer-readable storage medium of claim 8, wherein thecall event comprises one of a call origination event and a calltermination event.
 10. The non-transitory computer-readable storagemedium of claim 8, comprising generating as the message as one of anunstructured supplementary service data message, a short message servicemessage, and a SIP message over at least one of GPRS, EDGE, UMTS, CDMAEV-DO, WiMAX, and LTE.
 11. The non-transitory computer-readable storagemedium of claim 8, wherein the processor is further configured toperform: transmitting the message to a network node comprising one of aunstructured supplementary service data gateway, a short message servicecenter, a data gateway for at least one of GPRS, EDGE, UMTS, CDMA EV-DO,WiMAX, and LTE.
 12. The non-transitory computer-readable storage mediumof claim 8, wherein the processor is further configured to perform:processing the call according to the policy of the enterprise network.13. The non-transitory computer-readable storage medium of claim 8,wherein the intelligent network simulator application is stored on asubscriber identity module of the mobile terminal, and wherein themobile terminal is capable of configuring the intelligent networksimulator application as a call observer function on the mobileterminal.
 14. A system, comprising: a carrier network including a firstgateway server; and an enterprise network including a second gatewayserver communicatively coupled with the first gateway server; wherein acall event is received by an intelligent network simulator applicationoperating on a mobile terminal which collects information related to thecall event and generates a message including the information collectedby the intelligent network simulator application; wherein the message istransmitted to the first gateway server, which recognizes the message ascomprising a simulated intelligent network trigger, and which informsthe second gateway server of the simulated intelligent network trigger;wherein the second gateway server process the simulated intelligentnetwork trigger according to a policy of the enterprise network; andwherein the message informs the intelligent network simulatorapplication operating on the mobile terminal to perform at least one ofestablish the call event, answer the call event, disconnect the callevent and abandon the call event.
 15. The system of claim 14, whereinthe call event comprises one of a call origination event and a calltermination event.
 16. The system of claim 14, wherein the messagecomprises one of an unstructured supplementary service data message, ashort message service message, and a SIP message over at least one ofGPRS, EDGE, UMTS, CDMA EV-DO, WiMAX and LTE.
 17. The system of claim 14,wherein the intelligent network simulator application is stored on asubscriber identity module of the mobile terminal, and wherein theintelligent network simulator application identifies the call event andgenerates the message.